home *** CD-ROM | disk | FTP | other *** search
- Path: ren.cei.net!usenet
- From: Russell Reed <rreed@acxiom.com>
- Newsgroups: comp.sys.cbm
- Subject: Re: NTSC vs PAL questions...
- Date: Thu, 18 Apr 1996 08:45:04 -0700
- Organization: Acxiom Corp.
- Message-ID: <31766380.31F7@acxiom.com>
- References: <4kd7v5$r7e@calvino.alaska.net> <316B7B36.6E6C@esbjehs.dk> <316BAF26.1B9E@ludat.lth.se> <316CA3B3.7173@esbjehs.dk>
- NNTP-Posting-Host: gatekeeper.acxiom.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- X-Mailer: Mozilla 2.01 (Win16; I)
-
- Ejner wrote:
- >
- > In addition: The fewer screen updates on the PAL machines gives the
- > machines more time before the next screen update (more rastertime), which
- > can be used for even more or heavier calculations each frame...
- >
- > If anyone knows which rasterlines available on PAL machines are NOT
- > available on NTCS┤s, please share your knowledge!... Is this the only
- > difference you have to consider when NTCS-fixing?
-
- NTSC only has rasterlines through hex $106, where PAL goes up to
- somewhere around $150/$160 I think. The other difference is that
- on a PAL machine, there are 63 processor cycles per scan line
- but 65 on an NTSC machine. This has to be considered for raster
- routines.
-
- Russell Reed
- Decomp/Style
-